Requires a new experiment-core version to update the version and type.

I'm still getting my bearings on this, so I apologize if is a trivial question: Is the intended use for this meant for to configure tracking on a per fetch request basis or for all requests for a customer?

If this is intended to be an option for individual fetch requests to be made with and without tracking, then this seems fine. However, if the feature is meant more for a means for a user to wholesale turn on/off tracking, then it might be a better idea to set this on a client config level to prevent having to remember to set the flags for each place you might call fetch in your codebase.

I'm still getting my bearings on this, so I apologize if is a trivial question: Is the intended use for this meant for to configure tracking on a per fetch request basis or for all requests for a customer?

If this is intended to be an option for individual fetch requests to be made with and without tracking, then this seems fine. However, if the feature is meant more for a means for a user to wholesale turn on/off tracking, then it might be a better idea to set this on a client config level to prevent having to remember to set the flags for each place you might call fetch in your codebase.

This would be for individual fetch requests. Since this is server-side SDK, and an instance of experiment SDK is shared throughout the service lifecycle, each fetch request should be for a different end user. If customer logic determine that we shouldn't track events for this user (ex. bot), then they can do it through these options.

📝 Documentation updates detected!

New suggestion: Document FetchOptions for Node.js Experiment SDK

Thanks for the explanation. This makes a lot more sense to me now after looking at some of the other work around this request. 🙏